System and method for managing relationships between brokers and traders

ABSTRACT

According to one embodiment, a method of managing access to a trading network is provided. A first network login request for a first user is received from a client application. The first network login request includes first authentication information. Based at least on the first authentication information, the first network login request is approved, which authorizes the first user to access the trading network. One or more associated users for which the first user is authorized to act as a proxy is identifying from a plurality of users. User profile information for one of the associated users is obtained and communicated to the client application. The user profile information includes information regarding the second user that can be used to allow the first user to engage in trading activity via the trading network on behalf of the second user.

TECHNICAL FIELD OF THE INVENTION

This invention relates in general to trading markets and, moreparticularly, to a system and method for managing relationships betweenbrokers and traders in a trading network.

BACKGROUND OF THE INVENTION

In order to engage in trading activity with a trading exchange, such asa stock exchange for example, traders have traditionally used brokers toassist them with transactions in the trading exchange. A broker hasaccess to the trading exchange and acts as a middleman between a traderand the trading exchange, thus interacting with the trading exchange onbehalf of the trader, such as to place, modify, monitor, or cancelvarious trading orders for various tradable instruments. Thus, thetrader does not need direct access to the trading exchange and does notneed to spend their time monitoring the trading exchange and, inparticular, their existing trading orders.

In recent years, as investors have become more self-sufficient andcomfortable with computers, online trading has gained a widespreadacceptance for trading. For example, online trading systems have beencreated which facilitate the trading of financial instruments such asstocks, bonds, currency, futures, or other suitable financialinstruments. Using such systems, investors may have direct access totheir accounts information and may initiate transactions nearlyinstantaneously and, in some cases, 24 hours a day.

SUMMARY OF THE INVENTION

In accordance with the present invention, systems and methods formanaging relationships between brokers and traders in a trading networkare provided. According to one embodiment, a method of managing accessto a trading network is provided. A first network login request for afirst user is received from a client application. The first networklogin request includes first authentication information. Based at leaston the first authentication information, the first network login requestis approved, which authorizes the first user to access the tradingnetwork. One or more associated users for which the first user isauthorized to act as a proxy is/are identified from a plurality ofusers. User profile information for one of the associated users isobtained and communicated to the client application. The user profileinformation includes information regarding the second user that can beused to allow the first user to engage in trading activity via thetrading network on behalf of the second user.

According to another embodiment, another method of managing access to atrading network is provided. An attachment request from a clientapplication associated with a first user is received at a broker proxyserver. The attachment request includes a request to attach the firstuser to a second user and indicates whether the second user is a passivetrader or an active trader. A user relationship between the first userand the second user is established and stored. If the attachment requestindicates that the second user is a passive trader, an association isestablished between the user relationship and a first connection betweenthe broker proxy server and a trading system. The established userrelationship and the established first association allow the first userto engage in trading activity in the trading system on behalf of thesecond user via the first connection. Alternatively, if the attachmentrequest indicates that the second user is an active trader, it isdetermined whether the second user is logged into the trading system. Ifit is determined that the second user is logged into the trading system,a second association is established between the user relationship and asecond connection between the broker proxy server and the tradingsystem. The established user relationship and the established secondassociation allow the first user to engage in trading activity in thetrading system on behalf of the second user via the second connection.

Various embodiments of the present invention may benefit from numerousadvantages. It should be noted that one or more embodiments may benefitfrom some, none, or all of the advantages discussed below.

One advantage of the invention is that an electronic trading network isprovided in which one or more brokers may engage in trading activity ina trading system, such as a trading exchange for a particular type ofinstrument, on behalf of a particular trader. For example, supposing abroker permitted to act on behalf of the particular trader places atrading order in the trading system on behalf of the particular trader,another broker that is also permitted to act on behalf of the particulartrader may manage the trading order, which may include changing orcanceling the trading order, for example. In this manner, multiplebrokers may manage a single trader via an electronic network.

Another advantage of the present invention is that a broker proxy serverestablishes and manages relationships between brokers and traders thatare used to route messages between users (brokers and traders) and atrading system. As a result, messages sent from the trading systemregarding trading orders associated with a particular trader may berouted to the proper users, which may include the particular trader aswell as each interested broker (such as, for example, each broker thatis permitted to act on behalf of the particular trader).

Other advantages will be readily apparent to one having ordinary skillin the art from the following figures, descriptions, and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present invention and forfurther features and advantages, reference is now made to the followingdescription, taken in conjunction with the accompanying drawings, inwhich:

FIG. 1 illustrates an example trading network in which brokers areallowed to engage in trading activity on behalf of managed tradersaccording to an embodiment of the present invention;

FIG. 2 illustrates an example method of a broker logging into thenetwork of FIG. 1 in accordance with an embodiment of the presentinvention;

FIG. 3 illustrates an example method of a first broker “attaching” to amanaged trader in accordance with an embodiment of the presentinvention;

FIG. 4 illustrates an example method of a second broker “attaching” tothe same managed trader in accordance with an embodiment of the presentinvention;

FIG. 5 illustrates an example method of a broker logging off andsubsequently logging back in and “re-attaching” to a managed trader inaccordance with an embodiment of the present invention;

FIG. 6 illustrates an example table stored in association with anauthentication manager of the network of FIG. 1 in accordance with oneembodiment of the invention;

FIG. 7 illustrates an example table stored in association with a brokerproxy server of the network of FIG. 1 in accordance with one embodimentof the invention;

FIGS. 8A-8B illustrate a method of messaging within the system of FIG. 1in accordance with an embodiment of the present invention; and

FIG. 9 illustrates an example carrier message used for messaging via thetrading network of FIG. 1 in accordance with an embodiment of theinvention.

DETAILED DESCRIPTION OF THE DRAWINGS

Example embodiments of the present invention and their advantages arebest understood by referring now to FIGS. 1 through 9 of the drawings,in which like numerals refer to like parts.

In general, an electronic trading network is provided in which one ormore brokers may collectively or simultaneously manage trading orders onbehalf of a managed trader. For example, if a first broker that ispermitted to act on behalf of the managed trader places a trading orderat a trading system (such as a stock market, for example) on behalf ofthe particular trader, a second broker that is also permitted to act onbehalf of the managed trader may manage the trading order (which mayinclude changing or canceling the trading order, for example) as well asplace other trading orders at the trading system. Thus, multiple brokersmay manage a single trader via an electronic network.

FIG. 1 illustrates an example trading network 10 in which brokers areallowed to engage in trading activity on behalf of managed tradersaccording to an embodiment of the present invention. As shown, network10 includes one or more unmanaged trader terminals 12, managed traderterminals 14, broker terminals 16, session managers 18, authenticationmanagers 20, gateways 22, broker proxy servers 24 and trading systems26. Each component of network 10 may include any hardware, software orcombination thereof suitable to perform the functions of such componentsdiscussed herein. The components of trading network 10 are connected byvarious communication links 30 a through 30 g. Collectively, links 30 athrough 30 g may be referred to as communication network 30.Communication network 30, or various communication links 30 a through 30g, may include one or more local area networks (LANs), metropolitan areanetworks (MANs), wide area networks (WANs), wireless local area networks(WLANs), virtual private networks (VPNs), intranets, portions of theInternet, or any other appropriate wireline, optical, wireless, or otherlinks suitable to facilitate communication of data in a networkenvironment. Any of the various components of trading network 10 may beco-located with, or physically and/or geographically distributed from,any other components of trading network 10. In addition, variouscomponents of trading network 10 may be completely or partiallyintegrated with each other.

Each unmanaged trader terminal 12 hosts an unmanaged trader application32 that provides an unmanaged trader 34 access to engage in tradingactivity via one or more trading systems 26 of trading network 10. Eachunmanaged trader terminal 12 and application 32 may include a computersystem and appropriate software to allow unmanaged trader 34 to engagein trading activity via trading network 10. As used in this document,the term “computer” refers to any suitable device operable to acceptinput, process the input according to predefined rules, and produceoutput, for example, a personal computer, workstation, network computer,wireless data port, wireless telephone, personal digital assistant, oneor more processors within these or other devices, or any other suitableprocessing device. An unmanaged trader terminal 12 may also include oneor more human interfaces, such as a mouse, keyboard, or pointer, forexample.

An unmanaged trader 34 is a trader (such as an individual or group ofindividuals) that may engage in trading activity via trading network 10on behalf of itself. For example, an unmanaged trader 34 may managetrading orders via one or more trading systems 26 on its own behalf (inother words, without using a broker). In this manner, an unmanagedtrader 34 may trade with other traders 34 and/or 38 via one or moretrading systems 26.

As used throughout this document, “managing” a trading order includesdetermining the parameters of a new trading order (such as theinstrument, price, size, and type of order), submitting a new tradingorder, monitoring an existing trading order, altering an existingtrading order (such as changing the price, size, or type of the order,for example), canceling an existing trading order and/or any other anysuitable functions regarding a new or existing trading order in atrading system. In addition, as used throughout this document, “engagingin trading activity” includes at least managing trading orders.

Similar to unmanaged trader terminals 12, each managed trader terminal14 hosts a managed trader application 36 that provides a managed trader38 access to engage in trading activity via one or more trading systems26 of trading network 10. Each managed trader terminal 14 andapplication 36 may include a computer system and appropriate software toallow managed trader 38 to engage in trading activity via tradingnetwork 10.

A managed trader 38 is a trader (such as an individual or group ofindividuals) that may engage in trading activity via trading network 10on behalf of itself, as well as authorizing one or more brokers 40 toengage in trading activity on behalf of the managed trader 38. Forexample, a managed trader 38 may manage trading orders via one or moretrading systems 26 on its own behalf, as well as authorizing one or morebrokers 40 to manage trading orders via such trading systems 26 onbehalf of the managed trader 38. In this manner, a managed trader 38 maytrade with other traders 34 and/or 38 via one or more trading systems26.

Each broker terminal 16 hosts a broker application 42 that provides abroker 40 access to engage in trading activity on behalf of one or moremanaged traders 38 via trading network 10. Broker terminal 16 and brokerapplication 42 may include a computer system and appropriate software toallow broker 40 to engage in trading activity via trading network 10.

In some embodiments, a broker 40 is an individual, group of individuals,or other entity that is authorized to engage in trading activity viatrading network 10 on behalf of one or more managed traders 38, but noton its own behalf. For example, a broker 40 may manage trading ordersvia one or more trading systems 26 on behalf of a number of managedtraders 38, but not on its own behalf. Thus, in such embodiments, abroker 40 may not trade on its own behalf with other brokers 40 ortraders 34 or 38 via trading systems 26. In other embodiments, a broker40 may be permitted to act as a broker as well as a trader. In suchembodiments, a broker 40 may manage trading orders via one or moretrading systems 26 on behalf of managed traders 38, as well as on itsown behalf.

For a broker 40 authorized to act on behalf of a managed trader 38,trading network 10 generally allows the broker 40 to manage tradingorders collectively or simultaneously with the managed trader 38, aswell as with other brokers 40 authorized to act on behalf of the managedtrader 38. Thus, if broker 40 and the managed trader 38 are logged intoa trading system 26, both the broker 40 and the managed trader 38 maymanage trading orders in the trading system 26 on behalf of the managedtrader 38, including managing different trading orders as well as thesame trading orders. For example, if the broker 40 places a tradingorder in the trading system 26 on behalf of the managed trader 38, themanaged trader 38 may manage the trading order (such as altering orcanceling the trading order, for example), as well as place othertrading orders in the trading system. Thus, the broker 40 and themanaged trader 38 may co-manage trading orders on behalf of the managedtrader 38.

Similarly, if multiple brokers 40 that are each permitted to act onbehalf of a managed trader 38 are logged into a trading system 26, eachof the brokers 40 may manage trading orders in the trading system 26 onbehalf of the managed trader 38, including managing different tradingorders as well as the same trading orders. For example, if a firstbroker 40 that is permitted to act on behalf of the managed trader 38places a trading order at the trading system 26 on behalf of the managedtrader 38, a second broker 40 that is also permitted to act on behalf ofthe managed trader 38 may manage the trading order (such as changing orcanceling the trading order, for example), as well as place othertrading orders at the trading system on behalf of the managed trader 38.In this manner, multiple brokers may co-manage trading orders on behalfof a managed trader 38.

Each managed trader 38 may be either an active trader or a passivetrader. A broker 40 may engage in trading activity on behalf of apassive trader regardless of whether the passive trader is actuallylogged into trading network 10, while a broker 40 may engage in tradingactivity on behalf of an active trader only if the active trader isactually logged into trading network 10.

Brokers 40, managed traders 38 and unmanaged traders 36 may collectivelybe referred to as users 44 of trading network 10. It should beunderstood that in alternative embodiments, the relationships describedherein between brokers 40, managed traders 38 and unmanaged traders 36may apply similarly between other types of users of trading network 10.For example, in one alternative embodiment, one trader 34 or 38 may havea broker-trader relationship with another trader 34 or 38.

Applications 32, 36 and 42 may be referred to as client applications andmay include front-end applications that can connect with sessionmanagers 18 in order to access trading network 10. A session manager 18generally manages communication sessions between an application 32, 36or 42 and other portions of trading network 10. In the embodiment shownin FIG. 1, session manager 18 cooperates at least with an application32, 36 or 42, authentication manager 20, and gateways 22 to provide auser 44 access to trading systems 26. For example, session manager 18may establish and/or manage connections with particular gateways 22allowing communications between an application 32, 36 or 42 andparticular trading systems 26. In some embodiments, a particular sessionmanager 18 may be connected to a number of applications 32, 36 or 42such that a number of users 44 may access trading network 10 via theparticular session manager 18.

An authentication manager 20 generally manages the authentication ofusers 44 attempting to login to trading network 10. Authenticationmanager 20 may include memory 50 that may store, for each user ofnetwork 10, user login, or authentication, data 52, user profile data54, and user relationship data 56. User login data 52 includes variousinformation, such as login IDs and passwords, associated withauthorizing a user 44 access to network 10. User profile data 54includes various information regarding the respective user, such aswhich trading systems 26 in which that user 44 is permitted to trade,which types of orders that user 44 is permitted to submit, and formanaged traders 38, whether the trader 38 is an active or passivetrader, for example. User relationship data 56 identifies, for eachbroker 40, the managed traders 38 for which that broker 40 is authorizedto engage in trading activity on behalf of via network 10, and for eachmanaged trader 38, the one or more brokers 40 that are authorized to acton behalf of that managed trader 38. Thus, user relationship data 56defines a number of broker-trader relationships between brokers 40 andmanaged trader 38.

Memory 50 may include one or more suitable databases or memory devices,such as one or more SYBASE™ databases, INGRESS™ databases, ORACLE™databases, random access memories (RAMs), read-only memories (ROMs),dynamic random access memories (DRAMs), fast cycle RAMs (FCRAMs), staticRAM (SRAMs), field-programmable gate arrays (FPGAs), erasableprogrammable read-only memories (EPROMs), or electrically erasableprogrammable read-only memories (EEPROMs), for example.

An authentication manager 20 manages the authentication of users 44attempting to login to trading network 10 at least by comparing logininformation received from an application 32, 36 or 40 with appropriateuser login data 52 stored in memory 50. An authentication manager 20also provides functionality for managing broker-trader relationships,including managing access for a broker 40 to act on behalf of itsassociated managed traders 38. For example, as described in greaterdetail below with reference to FIG. 2, during or after the login of abroker 40, an authentication manager 20 may provide the broker 40 (orthe broker application 42 or session manager 18 associated with thatbroker 40) a list of managed traders 38 for which the broker 40 isauthorized to act on behalf of, as well as a list of each trading system26 in which each of such managed traders 38 is permitted to trade, basedon user profile data 54 and user relationship data 56. In someembodiments, the authentication manager 20 may also identify for thesession manager 18 associated with the broker 40, the appropriategateways 22 through which particular trading systems 26 may be accessed.

Gateways 22 are intermediate nodes within trading network 10 that mayprovide a connection from a session manager 18 to a trading system 26(for example, see communication link 30 f), or to a broker proxy server24 which is connected to a trading system 26 (for example, seecommunication links 30 e and 30 g).

A broker proxy server 24 manages user relationships between brokers 40and managed traders 38 and routes messages to and from trading systems26 according to such user relationships. The broker proxy server 24manages the “attachment” of brokers 40 to managed traders 38 whichallows the brokers 40 to engage in trading activity with one or moretrading systems 26 on behalf of such “attached” managed traders 38. Asdescribed in greater detail below with reference to FIG. 3, attachmentincludes establishing an appropriate connection between a gateway 22 anda trading system 26 which allows communication between a brokerapplication 42 and the trading system 26 so that a broker 40 using thebroker application 42 can engage in trading activity via the tradingsystem 26 on behalf of a managed trader 38.

Each broker proxy server 24 includes memory 60 that may store userrelationship data 62, connection data 64 and user status data 66. Userrelationship data 62 may include any number of user relationshipsbetween a managed trader 38 and a broker 40 that is currently “attached”to that managed trader 38. Connection data 64 may include dataidentifying connections between broker proxy server 24 and tradingsystem 26, as well as associations between such connections and userrelationships that have been established. User status data 66 mayinclude data regarding the current status of various users 44 of tradingnetwork 44, such as whether each user 44 is logged into network 10 andfurther whether each user 44 is logged into trading system 26. Memory 60may include one or more suitable databases or memory devices, such asdescribed above with reference to memory 50.

In some embodiments, communication links 30 a through 30 g may providevarious channels of communications via network 10. For example, in oneembodiment, such communication channels include a market data channelfor communicating data such as market data and trading orders, and anadministration channel for communicating administrative or control data.In this embodiment, broker proxy server 24 provides a proxy between agateway 22 and a trading system 26 only for the administration channel,and the gateway 22 continues to connect directly to the trading system26 market data channel or to a proxy of the market data channel providedby the trading system 26.

A trading system 26 may manage trading transactions between users 44 ofnetwork 10. For example, a trading system 26 may receive trading orders(such as orders to buy or sell a particular instrument) from traders 34and/or 38 and to manage or process those trading orders such thatfinancial transactions among and between traders 34 and/or 38 areperformed. A trading system 26 may include or communicate with one ormore market centers, which may comprise all manner of order executionvenues including exchanges, Electronic Communication Networks (ECNs),ATFs and market makers. A market center maintains a bid and offer pricein a given trading product by standing ready, willing, and able to buyor sell at publicly quoted prices.

In some embodiments, each trading system 26 represents a differentmarket. For example, different trading systems 26 within trading network10 may be provided for trading different types of instruments, such asNYSE stocks, US Treasuries, or Japanese government bonds, for example.In some embodiments, each broker 40 and each trader 34 and 38 ispermitted to trade in particular ones (or all) of the trading systems 26within trading network 10, based on a variety of factors.

Broker Login

FIG. 2 illustrates an example method of a broker 40 logging into network10 in accordance with an embodiment of the present invention. At step100, a broker 40, referred to herein as Broker X, uses a broker terminal16 to launches a broker application 42 hosted by the broker terminal 16.At step 102, Broker X enters various authentication information such asa user ID and a password into an interface, such as a graphical userinterface (GUI), provided by broker application 42. At step 104, brokerapplication 42 forwards a network login request including theauthentication information to an authentication manager 20. The networklogin request is a request to log Broker X into trading network 10 suchthat Broker X has access to trading network 10.

At step 106, authentication manager 20 determines whether to approve thenetwork login request based at least on the authentication information(for example, a user ID and password) included in the network loginrequest. To make this determination, authentication manager 20 maycompare the authentication information received in the network loginrequest with user login data 52 stored in memory 50. If theauthentication manager 20 rejects the network login request, anotification that the network login request was rejected is communicatedto broker application 42 at step 108 to inform Broker X. However, if theauthentication manager 20 approves the network login request, executionproceeds to step 110, where authentication manager 20 logs Broker X intonetwork 10.

At step 112, authentication manager 20 identifies that the network loginrequest was submitted by a broker 40 (namely, Broker X), such as basedon authentication information included in the broker's network loginrequest. At step 114, as a result of identifying that the network loginrequest was received from a broker 40, authentication manager 20identifies, based on user relationship data 56 stored in memory 50, eachmanaged trader 38 for which Broker X is authorized to engage in tradingactivity on behalf of. These managed traders 38 are referred to hereinas associated traders 38. Authentication manager 20 communicates a loginnotification, as well as the list of identified associated traders 38,to broker application 42 at step 116. The login notification indicatesthat the network login request for Broker X was approved and that BrokerX was logged into trading network 10. The list of identified associatedtraders 38 communicated to broker application 42 includes an indicationof whether each associated trader 38 is an active or passive trader.

In addition, at step 118, authentication manager 20 identifies, based onuser profile data 54 regarding Broker X, each trading system 26 to whichBroker X is authorized access (such as for engaging in trading activityon behalf of associated traders 38). At step 120, for each identifiedtrading system 26, authentication manager 20 determines a gateway 22through which broker application 42 may access that trading system 26.At step 122, authentication manager 20 communicates to brokerapplication 42 the list of trading systems 26 to which Broker X isauthorized access. At step 124, authentication manager 20 communicatesto the session manager 18 associated with the broker application 42 thegateway 22 determined for each trading system 26 to which Broker X isauthorized access.

At step 126, broker application 42 generates and communicates toauthentication manager 20 a network login request for each identifiedassociated trader 38. The network login request for each associatedtrader 38 includes a request to authenticate one of the associatedtraders 38. In this embodiment, network login requests for eachassociated trader 38 are automatically generated and submitted toauthentication manager 20 for approval. In an alternative embodiment,network login requests for each associated trader 38 are generated inresponse to commands entered by Broker X. The network login request foreach associated trader 38 may include authentication informationassociated with the associated trader 38, such that the authenticationmanager 20 may perform an authentication of the associated trader 38.Such authentication information may have been received by brokerapplication 42 from authentication manager 20 during the login processfor Broker X. Alternatively, at least a portion of the requiredauthentication information included in the network login request foreach associated trader 38 is manually entered by Broker X, which mayprovide an additional level of security.

At step 128, authentication manager 20 approves the network loginrequest for each associated trader 38 and generates a virtual loginsession for that associated trader 38. The virtual login session for anassociated trader 38 is distinct from whether or not that associatedtrader 38 is actually logged in to network 10 on its own behalf. As aresult of approving the network login request for each associated trader38, authentication manager 20 retrieves user login data 52 and userprofile data 54 regarding each associated trader 38 from memory 50 andcommunicates the retrieved user profile data 54 to broker application 42at step 130. The user login data 52 for each associated trader 38includes various information, such as login IDs and passwords,associated with authorizing such associated traders 38 access to network10. The user profile data 54 communicated to broker application 42 foreach associated trader 38 includes information regarding that trader 38that can be used to allow Broker X to engage in trading activity viatrading network 10 on behalf of that trader 38. For example, userprofile data 54 communicated to broker application 42 for eachassociated trader 38 may identify (1) each trading system 26 to whichthe trader 38 is permitted access for trading activity, (2) one or moreparameters defining the permitted trading activity for the trader 38 ineach of such trading systems 26, and/or (3) whether the trader 38 is apassive trader or an active trader.

Attachment

FIG. 3 illustrates an example method of Broker X “attaching” to amanaged trader 38 in accordance with an embodiment of the presentinvention. The method shown in FIG. 3 may follow or occur subsequent tothe method shown in FIG. 2.

At step 150, Broker X selects, via a GUI provided by broker application42, one of the associated traders 38 that Broker X wishes to trade orotherwise act on behalf of in a particular trading system 26. Theselected trader 38 is referred to herein as Trader Y. At step 152,broker application 42 generates and communicates to broker proxy server24 an attachment request to “attach” to Trader Y for the particulartrading system 26. The attachment request comprises a request toestablish and store a relationship between Broker X and Trader Y. Theattachment request includes an indication of whether Trader Y is anactive trader or a passive trader.

At step 154, broker proxy server 24 determines whether Broker X isauthorized to attach to Trader Y (in other words, whether Broker X isauthorized to act as a broker on behalf of Trader Y). This may involvebroker proxy server 24 communicating an attachment authorization queryto authentication manager 20 which identifies Broker X and Trader Y, andreceiving from the authentication manager 20 a determination (based onuser relationship data 56) of whether Broker X is authorized to engagein trading activity on behalf of Trader Y. If broker proxy server 24determines that Broker X is not authorized to attach to Trader Y, brokerproxy server 24 rejects the attachment request and notifies brokerapplication 42 accordingly at step 156. However, if broker proxy server24 determines that Broker X is authorized to attach to Trader Y, themethod continues to step 158. In some embodiments, broker proxy server24 assumes that all attachment requests received from brokerapplications 38 are valid, and automatically approves such requests. Insuch embodiments, step 154 is not performed.

At step 158, broker proxy server 24 attaches Broker X to Trader Y byestablishing a user relationship between Broker X and Trader Y. Theestablished user relationship is stored in table 60 as user relationshipdata 62 at step 160. User relationship data 62 may also include userrelationships between Trader Y and each other broker 40 that iscurrently attached to Trader Y. In addition, user relationship data 62may also include user relationships between Broker X and other selectedtraders 38 to which Broker X has already attached. At step 162, brokerproxy server 24 communicates an attachment notification to allinterested users 44, including (1) the broker application 42 associatedwith Broker X; (2) the trader application 36 associated with Trader Y;and (3) the broker applications 42 associated with other brokers 40monitoring the status of Trader Y, if any, which may include all otherbrokers 40 currently attached to Trader Y or all other brokers 40 loggedin to network 10 who are permitted to act on behalf of Trader Y. Theattachment notification indicates that Broker X has attached to TraderY. At step 164, the relevant broker application(s) 42 and traderapplication 36 are updated to indicate to respective broker(s) 40 andTrader Y that Broker X has attached to Trader Y, such as by updating aGUI display, for example.

In order for Broker X to engage in trading activity via the particulartrading system 26 on behalf of Trader Y, a connection between the brokerproxy server 24 is assigned to the user relationship between Broker Xand Trader Y. The manner in which such a connection is assigned dependson whether Trader Y is an active trader or a passive trader. Thus, atstep 166, broker proxy server 24 determines whether Trader Y is anactive trader or a passive trader based on information included in theattachment request.

If Trader Y is a passive trader, the method continues to step 168. Atstep 168, broker proxy server 24 determines whether Trader Y is alreadylogged in to the particular trading system 26, such as based on thecurrent user status data 66 stored in memory 60. If Trader Y iscurrently logged into the particular trading system 26, broker proxyserver 24 identifies the particular connection 30 g through which TraderY is connected to the particular trading system 26 at step 170. At step172, broker proxy server 24 establishes and stores as connection data 64an association between the user relationship between Broker X and TraderY (established at step 158) and the connection 30 g identified at step170. Thus, when Broker X subsequently sends a message to the particulartrading system 26 on behalf of Trader Y, broker proxy server 24 mayintercept the message, identify the user relationship between Broker Xand Trader Y, identify the appropriate connection 30 g associated withthe user relationship at step 170, and forward the message to thetrading system via the identified connection 30 g.

At step 174, broker proxy server 24 communicates a connectionnotification to all interested users 44, including: (1) the brokerapplication 42 associated with Broker X; (2) the trader application 36associated with Trader Y; and (3) the broker applications 42 associatedwith other brokers 40 monitoring the status of Trader Y, if any, whichmay include all other brokers 40 currently attached to Trader Y or allother brokers 40 logged in to network 10 who are permitted to act onbehalf of Trader Y. The connection notification indicates that Broker Xis connected to trading system 26 on behalf of Trader Y. At step 176,the relevant broker application(s) 42 and trader application(s) 36 areupdated to indicate to respective broker(s) 40 and Trader Y that BrokerX is connected to trading system 26 on behalf of Trader Y, such as byupdating a GUI display, for example. In particular, the brokerapplication 42 associated with Broker X may provide a GUI allowingBroker X to engage in trading activity in trading system 26 on behalf ofTrader Y.

Accordingly, at step 178, Broker X may now engage in trading activity intrading system 26 on behalf of Trader Y via broker application 42 andthe connection 30 g associated at step 170. Others brokers 40, if any,that are currently attached to Trader Y may continue to engage intrading activity in trading system 26 on behalf of Trader Y. Thus, atstep 178, Trader Y, Broker X, and other brokers 40 currently attached toTrader Y may collectively engage in trading activity in trading system26 on behalf of Trader Y, including collectively managing trading ordersin trading system 26. For example, supposing that one of Trader Y,Broker X, or another broker 40 currently attached to Trader Y places atrading order at trading system 26 on behalf of Trader Y, any or all ofTrader Y, Broker X, and other brokers 40 currently attached to Trader Ymay adjust, cancel or otherwise manage the trading order on behalf ofTrader Y.

Alternatively, if it is determined that Trader Y is not currently loggedin to the particular trading system 26, at step 180, broker proxy server24 determines a particular connection 30 g through which to communicatewith trading system 26. At step 182, broker proxy server 24 sends atrading system login request to the trading system 26 on behalf ofTrader Y via the particular connection 30 g. The trading system loginrequest is a request to log Trader Y into the trading system 26 onbehalf of Broker X. The trading system login request appears to thetrading system 26 as if it was received from Trader Y itself. At step184, the trading system 26 logs in Trader Y and communicates a loginnotification to broker proxy server 24 via the connection 30 g used atstep 182.

At step 185, broker proxy server 24 establishes and stores as connectiondata 64 an association between the user relationship between Broker Xand Trader Y (established at step 158) and the connection 30 g used atstep 182. At step 186, broker proxy server 24 communicates a connectionnotification to all interested users 44, such as described above withreference to step 174. The connection notification indicates that BrokerX is connected to trading system 26 on behalf of Trader Y. At step 188,the relevant broker application(s) 42 and trader application 36 areupdated, such as described above with reference to step 176.Accordingly, at step 190, Broker X may now engage in trading activity intrading system 26 on behalf of Trader Y via the connection 30 g used atsteps 182 and 184. Thus, Trader Y, Broker X, and other brokers 40currently attached to Trader Y may collectively engage in tradingactivity in trading system 26 on behalf of Trader Y, includingcollectively managing trading orders in trading system 26, as discussedabove with reference to step 178.

Alternatively, if it is determined at step 166 that Trader Y is anactive trader, the method continues to step 192. At step 192, brokerproxy server 24 determines whether Trader Y is already logged in to theparticular trading system 26, such as based on the current user statusdata 66 stored in memory 60. If Trader Y is currently logged in to theparticular trading system 26, broker proxy server 24 identifies theparticular connection 30 g through which Trader Y is connected to theparticular trading system 26 at step 194. At step 196, broker proxyserver 24 establishes and stores as connection data 64 an associationbetween the user relationship between Broker X and Trader Y (establishedat step 158) and the connection 30 g identified at step 194. Thus, whenBroker X subsequently sends a message to the particular trading system26 on behalf of Trader Y, broker proxy server 24 may intercept themessage, identify the user relationship between Broker X and Trader Y,identify the appropriate connection 30 g associated with the userrelationship at step 194, and forward the message to the trading systemvia the identified connection 30 g.

At step 198, broker proxy server 24 communicates a connectionnotification to all interested users 44, such as described above withreference to step 174. At step 200, the relevant broker application(s)42 and trader application 36 are updated, such as described above withreference to step 176. Accordingly, at step 202, Broker X may now engagein trading activity in trading system 26 on behalf of Trader Y via theconnection 30 g identified at step 194. Thus, Trader Y, Broker X, andother brokers 40 currently attached to Trader Y may collectively engagein trading activity in trading system 26 on behalf of Trader Y,including collectively managing trading orders in trading system 26, asdiscussed above with reference to step 178.

However, if it is determined at step 192 that Trader Y is not currentlylogged in to the particular trading system 26, broker proxy server 24does not associate a connection 30 g with the user relationship betweenBroker X and Trader Y (established at step 158). As a result, Broker Xis unable to send messages to, or receive messages from, trading system26 on behalf of Trader Y, at least until Trader Y logs into the tradingsystem 26, as discussed below. Thus, at step 204, broker proxy server 24waits for Trader Y to log into trading system 26. At some later time, atstep 206, Trader Y (via the trader application 36 associated with TraderY) submits a trading system login request to log into trading system 26,which trading system login request is intercepted by broker proxy server24. At step 208, broker proxy server 24 assigns, or uses, a particularconnection 30 g to forward the trading system login request to thetrading system 26. At step 210, broker proxy server 24 stores theparticular connection 30 g as connection data 64 and associates theparticular connection 30 g with the user relationship between Broker Xand Trader Y that was established at step 158. At step 212, the tradingsystem 26 logs Trader Y into the trading system 26 and communicates alogin notification to broker proxy server 24 via the connection 30 gused at step 208.

At step 214, broker proxy server 24 communicates a connectionnotification to all interested users 44, such as described above withreference to step 174. The connection notification indicates that TraderY is connected to trading system 26. At step 216, the relevant brokerapplication(s) 42 and trader application 36 are updated, such asdescribed above with reference to step 176. Accordingly, at step 218,Broker X may now engage in trading activity in trading system 26 onbehalf of Trader Y via the connection 30 g used at steps 208 and 212.Thus, Trader Y, Broker X, and other brokers 40 currently attached toTrader Y may collectively engage in trading activity in trading system26 on behalf of Trader Y, including collectively managing trading ordersin trading system 26, as discussed above with reference to step 178.

FIG. 4 illustrates an example method of another broker 40 “attaching” toTrader Y in accordance with an embodiment of the present invention. Themethod shown in FIG. 4 may follow or occur subsequent to the methodshown in FIG. 3. In some situations, after Broker X has been attached toTrader Y, other brokers 40 that are authorized to act on behalf ofTrader Y may attach to Trader Y, as shown as steps 230 through 248.

At step 230, a second broker 40, referred to herein as Broker Z, submitsan attachment request to “attach” to Trader Y, including a request toestablish the requested connection. At step 232, broker proxy server 24determines whether Broker Z is authorized to attach to Trader Y, such asdescribed above with reference to steps 154 and 156 of FIG. 3. AssumingBroker Z is authorized to attach to Trader Y, broker proxy server 24proceeds to the attachment process. At step 234, broker proxy server 24attaches Broker Z to Trader Y by establishing and storing as userrelationship data 62 a user relationship between Broker Z and Trader Y,such as described above with reference to steps 158 and 160 of FIG. 3.At step 236, broker proxy server 24 sends an attachment notification tointerested users 44, including Broker Z, Broker X, Trader Y, and otherinterested brokers 40, such as described above with reference to step162 of FIG. 3. The attachment notification indicates that Broker Z hasattached to Trader Y. At step 238, the relevant user applications 36 and42 are updated, such as described above with reference to step 164 ofFIG. 3.

At step 240, broker proxy server 24 identifies that a particularconnection 30 g is currently assigned, or is being used, forcommunications between broker proxy server 24 and trading system 26 onbehalf of Trader Y. Namely, the identified connection 30 g is theconnection 30 g associated with the user relationship between Broker Xand Trader Y at step 172, 185, 196, or 208 of the method of FIG. 3. Atstep 242, broker proxy server 24 establishes and stores as connectiondata 64 an association between the user relationship between Broker Zand Trader Y (established at step 234) and the connection 30 gidentified at step 240. Thus, when Broker Z subsequently sends a messageto the particular trading system 26 on behalf of Trader Y, broker proxyserver 24 may intercept the message, identify the user relationshipbetween Broker Z and Trader Y, identify the appropriate connection 30 gassociated with the user relationship at step 242, and forward themessage to the trading system via the identified connection 30 g.

At step 244, broker proxy server 24 communicates a connectionnotification to the broker application 42 associated with Broker Z. Theconnection notification indicates that a connection 30 g exists forcommunicating with trading system 26 on behalf of Trader Y. At step 246,the broker application 42 associated with Broker Z is updated toindicate that Broker Z may now place trading orders or otherwise engagein trading activity in trading system 26 on behalf of Trader Y. Inparticular, the broker application 42 associated with Broker Z mayprovide a GUI allowing Broker Z to engage in trading activity in tradingsystem 26 on behalf of Trader Y. Accordingly, at step 248, Broker Z maynow engage in trading activity in trading system 26 on behalf of TraderY via the connection 30 g associated with the user relationship at step242. Thus, Broker Z, Broker X, Trader Y, and other brokers 40 currentlyattached to Trader Y may collectively engage in trading activity intrading system 26 on behalf of Trader Y, including collectively managingtrading orders in trading system 26, as discussed above with referenceto step 178.

Detachment and Re-Attachment

FIG. 5 illustrates an example method of Broker X logging off and thenlogging back in to network 10 and “re-attaching” to a trader 38 inaccordance with an embodiment of the present invention. The method shownin FIG. 5 may follow or occur subsequent to the method shown in FIG. 3or FIG. 4.

At step 260, Broker X logs off of network 10, such as by selecting a“logoff” icon on a GUI display presented to Broker X by brokerapplication 42. At step 262, broker application 42 communicates a logoffnotification to broker proxy server 24 indicating that Broker X islogging off or has logged off of network 10. In response to receivingthe logoff notification, broker proxy server 24 “detaches” Broker X fromTrader Y at step 264, which includes deleting, writing over or otherwiseremoving the user relationship between Broker X and Trader Y establishedand stored in memory 60 at step 158 and 160 of the method shown in FIG.3.

At step 266, Broker X logs back into network 10, which may include theperformance of any or all of steps 100 through 130 discussed above withreference to the method of FIG. 2. At step 268, broker application 42communicates a login notification to broker proxy server 24 indicatingthat Broker X is logging back on or has logged back on to tradingnetwork 10. In response to receiving the login notification, brokerproxy server 24 automatically re-attaches Broker X to each managedtrader 38 to which Broker X was attached when Broker X previously loggedoff of network 10. The process of re-attaching Broker X to thepreviously Trader Y is described below with reference to steps 270through 278.

At step 270, broker proxy server 24 determines the current state of theconnection 30 g, if any, between broker proxy server 24 and the tradingsystem 26 for communicating with trading system 26 on behalf of TraderY. If broker proxy server 24 determines that the same connection 30 g isstill assigned, or being used, for communications on behalf of Trader Y,broker proxy server 24, at step 272, (1) re-attaches Broker X to TraderY by generating and storing as user relationship data 62 a userrelationship between Broker X and Trader Y, and (2) re-establishes andstores as connection data 64 an association between the connection 30 gand the user relation between Broker X and Trader Y. Accordingly, atstep 274, Broker X may now engage in trading activity in trading system26 on behalf of Trader Y via the same connection 30 g as was used beforeBroker X logged off at step 260.

Alternatively, if broker proxy server 24 determines at step 270 that anew connection 30 g has been assigned, or is being used, forcommunications on behalf of Trader Y, broker proxy server 24, at step276, (1) reattaches Broker X to Trader Y by generating and storing asuser relationship data 62 a user relationship between Broker X andTrader Y, and (2) establishes and stores as connection data 64 anassociation between the new connection 30 g and the user relationbetween Broker X and Trader Y. Accordingly, the method proceeds to step274, at which step Broker X may now engage in trading activity intrading system 26 on behalf of Trader Y via the new connection 30 g.

Alternatively, if broker proxy server 24 determines at step 270 that noconnection 30 g is currently assigned, or being used, for communicationson behalf of Trader Y—in other words, that Trader Y is not logged intotrading system 26—broker proxy server 24, at step 278, (1) reattachesBroker X to Trader Y by generating and storing as user relationship data62 a user relationship between Broker X and Trader Y, and (2)establishes (or attempts to establish) an association between aconnection 30 g and the user relationship between Broker X and Trader Y.The manner in which such a connection is assigned depends on whetherTrader Y is an active trader or a passive trader. If Trader Y is apassive trader, the process for establishing the association may includeone or more steps similar or identical to steps 180 through 190discussed above with reference to the method of FIG. 3. Alternatively,if Trader Y is an active trader, the process for establishing theassociation may include one or more steps similar or identical to steps204 through 218 discussed above with reference to the method of FIG. 3.Once the association has been established (which, in the case of anactive Trader Y may be postponed until Trader Y logs in trading system26, as discussed above with reference to step 204 of FIG. 3), the methodmay proceed to step 274, at which step Broker X may now engage intrading activity in trading system 26 on behalf of Trader Y via the newconnection 30 g.

FIG. 6 illustrates an example table 300 including login data 52, userprofile data 54, and user relationship data 56 stored in memory 50 forvarious users 44 (brokers 40 and traders 34 and 38) of network 10 inaccordance with one embodiment of the invention. For each user 44,column 302 indicates the user's user ID; column 304 indicates the user'spassword; column 306 indicates whether the user is a broker or trader;column 308 indicates whether the user is managed or unmanaged (appliesonly to traders 34 and 38, not brokers 40); column 310 indicates theauthorized user relationships for the user (applies only to brokers 40and managed traders 38, not unmanaged traders 34); column 312 indicateswhether the user is active or passive (applies only to managed traders38, not brokers 40 or unmanaged traders 34); column 314 indicates thetrading systems 26 which the user is permitted to access; and column 316indicates whether the user is currently logged into network 10. Logindata 52 may include the information stored in columns 302, 304, and 316.User profile data 54 may include the information stored in columns 306,308, 312 and 314. User relationship data 56 may include the informationstored in column 310.

FIG. 7 illustrates an example table 330 including user relationship data62, connection data 64, and user status data 66 stored in memory 60 forvarious users 44 (brokers 40 and traders 34 and 38) of network 10 inaccordance with one embodiment of the invention. For each trader 34 and38, column 332 indicates the trader's user ID; column 334 indicateswhether the trader is managed or unmanaged; column 336 indicates whetherthe trader is an active or passive trader; column 338 indicates whetherthe trader is logged into trading network 10; column 340 indicateswhether the trader is currently connected to, or logged into, thetrading system 26 (whether in response to a request from a trader or inresponse to a request from a broker 40 attempting to engage in tradingactivity on behalf of the trader); column 342 identifies the connection,if any, between the broker proxy server 24 and the trading system 26that has been assigned, or that is being used, for communicatingmessages associated with the trader between the broker proxy server 24and the trading system 26; column 344 indicates the brokers 40, if any,that are currently attached to the trader; and column 346 indicates thegateway 22 associated with each broker 40 identified in column 344. Userrelationship data 62 may include the information stored in column 344,connection data 64 may include the information stored in columns 340,342 and 244, and user status data 66 may include the information storedin columns 334, 336, 338 and 340.

Particular data stored in table 330 is dynamic over time. For example,the brokers 40 listed in column 344 change over time as brokers 40attach and detach from various managed traders 38. In addition, theconnections listed in column 342 may change over time as connections areassigned, reassigned or otherwise managed by broker proxy server 24.

FIGS. 8A-8B illustrate an example method of messaging within system 10in accordance with an embodiment of the present invention. As shown inFIG. 8A, at step 400, Broker X using broker application 42 logs intonetwork 10 according to the method shown in FIG. 2. As part of the loginprocess, authentication manager 20 identifies a particular tradingsystem 26 in which Broker X is permitted to trade, and sends to sessionmanager 18 associated with broker application 42 an identity of agateway 22 through which broker application 42 may communicate with theparticular trading system 26, as discussed above with reference to steps118 through 124 of the method of FIG. 2. At step 402, Broker X wishes toengage in trading activity in the particular trading system 26 on behalfof Trader Y, and thus attaches to Trader Y according to the method shownin FIG. 3. In particular, broker proxy server 24 establishes and storesa user relationship between Broker X and Trader Y, as described abovewith reference to steps 158 and 160 of FIG. 3. In this examplesituation, Trader Y is an active trader that is currently logged intothe particular trading system 26.

At step 404, broker proxy server 24 (1) identifies the connection 30 gthat is being used to communicate messages regarding trading activity ofTrader Y with trading system 26; (2) establishes and stores anassociation between the user relationship between Broker X and Trader Y(established at step 402) and the identified connection 30 g; (3) sendsa connection notification to all interested users 44, such as describedabove with reference to steps 194 through 198 of the method of FIG. 3.At step 406, broker application 42 associated with Broker X updates aGUI presented to Broker X such that Broker X may now engage in tradingactivity in trading system 26 on behalf of Trader Y via the connection30 g identified at step 404.

At step 408, another broker, Broker Z, logs into network 10 and attachesto Trader Y according to the method shown in FIG. 4. In particular,broker proxy server 24 establishes and stores a user relationshipbetween Broker Z and Trader Y, as described above with reference to step234 of FIG. 4. In addition, broker proxy server 24 establishes andstores an association between the user relationship between Broker Z andTrader Y (established at step 402) and the connection 30 g identified atstep 404. Thus, both Broker X and Broker Z may attach to, and may thusengage in trading activity on behalf of, Trader Y.

At some time, Broker X wishes to place a trading order at trading system26 on behalf of Trader Y. At step 410, Broker X submits, via a GUIprovided by broker application 42, a request to place the trading orderat trading system 26 on behalf of Trader Y. At step 412, brokerapplication 42 generates a trading message 500 that specifies Trader Y,as well as various other details of the requested trading order, such asthe type of order, the financial instrument, the price, and the size ofthe order, for example. Trading message 500 generated at step 412represents (or is similar or identical to) the trading message thatwould have been generated by the trader application 36 associated withTrader Y if Trader Y, rather than Broker X, had initiated the tradingorder request.

At step 414, broker application 42 generates a carrier message 502 fortrading message 500. At step 416, broker application 42 joins orotherwise associates carrier message 502 with trading message 500. Inone embodiment, broker application 42 encapsulates trading message 500within carrier message 502, as shown in FIG. 9.

FIG. 9 illustrates an example carrier message 502 in accordance with anembodiment of the invention. Carrier message 502 is a data packet thatincludes a header 504 that may contain protocol and routing information,and a payload 506 that includes a number of fields 508. A particularfield 508 includes the trading message 500 such that the trading message500 may be said to be encapsulated within carrier message 502. Header504 may include routing information that identifies the gateway 22identified at step 400 and the particular trading system 26 for whichtrading message 500 is intended. One or more fields 508 may includevarious other data, such as data indicating the message type of tradingmessage 500, for example.

Returning to FIG. 8A, at step 418, broker application 42 communicatescarrier message 502 toward the particular trading system 26 based onrouting information included in header 504. At step 420, carrier message502 is received by the gateway 22 and routed toward trading system 26.

At step 422, carrier message 502 is intercepted by broker proxy server24. At step 424, broker proxy server 24 de-encapsulates trading message500 from carrier message 502. At step 426, broker proxy server 24 thendelivers trading message 500 to the trading system 26 using theconnection 30 g associated (at step 404) with the user relationshipbetween Broker X and Trader Y based on information within tradingmessage 500, such as information identifying Trader Y. Trading message500 may include routing information that may be used to route tradingmessage 500 to the proper portion or module of trading system 26 suchthat trading system 26 may process trading message 500 appropriately. Atstep 428, the trading system 26 receives and processes trading message500, and places the requested trading order in a trading exchangemaintained by trading system 26. Trading message 500 appears to thetrading system 26 as if it was submitted by Trader Y.

As shown in FIG. 8B, at step 430, trading system 26 generates a tradingmessage 500′ that indicates that the requested trading order was placedin a trading exchange. At step 432, trading system 26 communicatestrading message 500′ toward Trader Y via the connection 30 g used atstep 426 of the method of FIG. 8A. At step 434, the broker proxy server24 intercepts trading message 500′. At step 436, broker proxy server 24forwards trading message 500′ toward the trading application 36associated with Trader Y.

At step 438, broker proxy server 24 identifies each broker 40 broker 40currently attached to Trader Y, including Broker X and Broker Z, basedon user relationship data 62 stored in memory 60. At step 440, brokerproxy server 24 generates a carrier message 502′ for each broker 40identified at step 438, including Broker X and Broker Z. As shown inFIG. 9, carrier message 502′ may be similar to carrier message 502. Theheader 504′ of each carrier message 502′ may include routing informationthat identifies the appropriate gateway 22 and particular brokerapplication 42 for which trading message 500′ is intended. One or morefields 508′ may include various other data, such as data indicating themessage type of trading message 500′, for example.

At step 442, broker application 42 joins or otherwise associates a copyor instance of trading message 500′ with each carrier message 502′. Inone embodiment, broker application 42 encapsulates a copy or instance oftrading message 500′ within each carrier message 502′. At step 444, thecarrier messages 502′ are communicated to each respective broker 40,including Broker X and Broker Z, according to routing informationincluded in each respective carrier message 502′. At step 446, thebroker application 42 associated with each broker 40 that receives oneof the carrier messages 502′ (including the broker applications 42 ofBroker X and Broker Z) de-encapsulates the trading message 500′ from thecarrier message 502′ and processes the trading message 500′ accordingly.Thus, by managing user relationship data 62, which indicates whichbrokers 40 are currently attached to a managed trader 38, broker proxyserver 24 may manage the routing of trading messages 500′ to theappropriate users 44.

Although an embodiment of the invention and its advantages are describedin detail, a person skilled in the art could make various alterations,additions, and omissions without departing from the spirit and scope ofthe present invention as defined by the appended claims.

1. A method of managing access to a trading network, comprising:receiving from a client application a first network login request for afirst user, the first login request including first authenticationinformation; approving the first network login request based at least onthe first authentication information, wherein approving the first loginnetwork request authorizes the first user to access the trading network;identifying from a plurality of users one or more associated users forwhich the first user is authorized to act as a proxy, the one or moreidentified associated users including a second user; obtaining userprofile information for the second user, the user profile informationincluding information regarding the second user that can be used toallow the first user to engage in trading activity via the tradingnetwork on behalf of the second user; and communicating the user profileinformation to the client application.
 2. The method of claim 1, furthercomprising: receiving from the client application a second network loginrequest for the second user; and approving the second network loginrequest to authorize the second user to access the trading network. 3.The method of claim 1, wherein the first user is a broker that isprevented from engaging in trading activity via the trading network onbehalf of itself.
 4. The method of claim 1, further comprising:identifying, based at least on the received first authenticationinformation, one or more trading systems to which the first user isauthorized access; and communicating to the client application a list ofthe identified trading systems.
 5. The method of claim 1, wherein theuser profile information identifies one or more trading systems to whichthe second user is authorized access for trading activity.
 6. The methodof claim 5, wherein the user profile information identifies, for eachidentified trading system, one or more parameters defining the permittedtrading activity for the second user in that trading system.
 7. Themethod of claim 1, wherein the user profile information identifieswhether the second user is a passive trader or an active trader, whereinthe first user may engage in trading activity on behalf of a passivetrader regardless of whether the passive trader is logged into thetrading network, and wherein the first user may engage in tradingactivity on behalf of an active trader only if the active trader islogged into the trading network.
 8. The method of claim 1, wherein thefirst user is a first broker; wherein the method further comprisesstoring a set of broker-trader relationships, each broker-traderrelationship defining a relationship between one of a plurality ofbrokers and one of a plurality of traders, the plurality of brokersincluding the first broker and the plurality of traders including theplurality of users; and wherein the one or more associated users forwhich the first user is authorized to act as a proxy are identified byidentifying from the set of broker-trader relationships eachbroker-trader relationship between the first broker and any one of theplurality of traders.
 9. The method of claim 1, further comprising:receiving an attachment request from the client application, theattachment request associated with a particular trading system andincluding a request to establish a user relationship between the firstuser and the second user; in response to the attachment request,establishing a user relationship between the first user and the seconduser; and establishing an association between the user relationship anda connection with the particular trading system; wherein the establisheduser relationship and the established association allow the second userto engage in trading activity in the particular trading system on behalfof the second user.
 10. The method of claim 9, further comprising:receiving an additional attachment request from an additional clientapplication associated with a third user, the additional attachmentrequest comprising a request to establish an additional userrelationship between the third user and the second user; in response tothe attachment request, establishing an additional user relationshipbetween the third user and the second user; and establishing anadditional association between the additional user relationship and theconnection with the particular trading system; wherein the establishedadditional user relationship and the established additional associationallow the third user to engage in trading activity in the particulartrading system on behalf of the second user.
 11. The method of claim 10,wherein the third user is a broker that is prevented from engaging intrading activity via the trading network on behalf of itself.
 12. Asystem for managing access to a trading network, the system comprisingan authentication manager operable to: receive from a client applicationa first network login request for a first user, the first network loginrequest including first authentication information; approve the firstnetwork login request based at least on the first authenticationinformation, wherein approving the first network login requestauthorizes the first user to access the trading network; identify from aplurality of users one or more associated users for which the first useris authorized to act as a proxy, the one or more identified associatedusers including a second user; obtain user profile information for thesecond user, the user profile information including informationregarding the second user that can be used to allow the first user toengage in trading activity via the trading network on behalf of thesecond user; and communicate the user profile information to the clientapplication.
 13. The system of claim 12, wherein the authenticationmanager is further operable to: receive from the client application asecond network login request for the second user; and approve the secondnetwork login request to authorize the second user to access the tradingnetwork.
 14. The system of claim 12, wherein the first user is a brokerthat is prevented from engaging in trading activity via the tradingnetwork on behalf of itself.
 15. The system of claim 12, wherein theauthentication manager is further operable to: identify, based at leaston the received first authentication information, one or more tradingsystems to which the first user is authorized access; communicate to theclient application a list of the identified trading systems.
 16. Thesystem of claim 12, wherein the user profile information identifies oneor more trading systems to which the second user is authorized accessfor trading activity.
 17. The system of claim 16, wherein the userprofile information identifies, for each identified trading system, oneor more parameters defining the permitted trading activity for thesecond user in that trading system.
 18. The system of claim 12, whereinthe user profile information identifies whether the second user is apassive trader or an active trader, wherein the first user may engage intrading activity on behalf of a passive trader regardless of whether thepassive trader is logged into the trading network, and wherein the firstuser may engage in trading activity on behalf of an active trader onlyif the active trader is logged into the trading network.
 19. The systemof claim 12, wherein the first user is a first broker; wherein theauthentication manager is further operable to store a set ofbroker-trader relationships, each broker-trader relationship defining arelationship between one of a plurality of brokers and one of aplurality of traders, the plurality of brokers including the firstbroker and the plurality of traders including the plurality of users;and wherein the one or more associated users for which the first user isauthorized to act as a proxy are identified by identifying from the setof broker-trader relationships each broker-trader relationship betweenthe first broker and any one of the plurality of traders.
 20. The systemof claim 12, further comprising a broker proxy server operable to:receive an attachment request from the client application, theattachment request associated with a particular trading system andincluding a request to establish a user relationship between the firstuser and the second user; in response to the attachment request,establish a user relationship between the first user and the seconduser; and establish an association between the user relationship and aconnection with the particular trading system; wherein the establisheduser relationship and the established association allow the second userto engage in trading activity in the particular trading system on behalfof the second user.
 21. The system of claim 20, wherein the broker proxyserver is further operable to: receive an additional attachment requestfrom an additional client application associated with a third user, theadditional attachment request comprising a request to establish anadditional user relationship between the third user and the second user;in response to the attachment request, establish an additional userrelationship between the third user and the second user; and establishan additional association between the additional user relationship andthe connection with the particular trading system; wherein theestablished additional user relationship and the established additionalassociation allow the third user to engage in trading activity in theparticular trading system on behalf of the second user.
 22. The systemof claim 21, wherein the third user is a broker that is prevented fromengaging in trading activity via the trading network on behalf ofitself.
 23. A method of managing access to a trading network,comprising: receiving at a broker proxy server an attachment requestfrom a client application associated with a first user, the attachmentrequest including a request to attach the first user to a second user,the attachment request indicating whether the second user is a passivetrader or an active trader; establishing and storing a user relationshipbetween the first user and the second user; if the attachment requestindicates that the second user is a passive trader, establishing a firstassociation between the user relationship and a first connection betweenthe broker proxy server and a trading system; wherein the establisheduser relationship and the established first association allow the firstuser to engage in trading activity in the trading system on behalf ofthe second user via the first connection; and if the attachment requestindicates that the second user is an active trader: determining whetherthe second user is logged into the trading system; and if it isdetermined that the second user is logged into the trading system,establishing a second association between the user relationship and asecond connection between the broker proxy server and the tradingsystem; wherein the established user relationship and the establishedsecond association allow the first user to engage in trading activity inthe trading system on behalf of the second user via the secondconnection.
 24. The method of claim 23, wherein the first connection andthe second connection are the same connection such that an associationis established between the user relationship and a particular connectionbetween the broker proxy server and the trading system regardless ofwhether the second user is a passive trader or an active trader.
 25. Themethod of claim 23, further comprising preventing the first user fromengaging in trading activity in the trading system on behalf of thesecond user if it is determined that the second user is not logged intothe trading system.
 26. The method of claim 23, wherein if it isdetermined that the second user is not logged into the trading system,the method further comprises: waiting to receive a trading system loginrequest from the second user; receiving the trading system login requestfrom the second user; and in response to receiving the trading systemlogin request from the second user, establishing a third associationbetween the user relationship and a third connection between the brokerproxy server and the trading system; wherein the established userrelationship and the established third association allow the first userto engage in trading activity in the trading system on behalf of thesecond user via the third connection.
 27. The method of claim 26,wherein the third connection and the second connection are the sameconnection such that an association is established between the userrelationship and a particular connection between the broker proxy serverand the trading system regardless of whether the second user is loggedin at the time the attachment request is received or logs in at a latertime.
 28. The method of claim 23, wherein the first user is a brokerthat is prevented from engaging in trading activity via the tradingnetwork on behalf of itself.
 29. The method of claim 23, furthercomprising determining whether the second user is authorized to attachto the first user.
 30. The method of claim 29, wherein determiningwhether the second user is authorized to attach to the first usercomprises: communicating an attachment authorization query to anauthentication manager, the attachment authorization query identifyingthe second user and the first user; and receiving from theauthentication manager a determination of whether the second user isauthorized to engage in trading activity on behalf of the first user.31. The method of claim 23, further comprising: receiving an additionalattachment request from an additional client application associated witha third user, the additional attachment request including a request toattach the third user to a second user; establishing and storing anadditional user relationship between the third user and the second user;if the first association is established, establishing an additionalassociation between the additional user relationship and the firstconnection between the broker proxy server and the trading system;wherein the established additional user relationship and the establishedadditional association allow the third user to engage in tradingactivity in the trading system on behalf of the second user via thefirst connection; and if the second association is established,establishing an additional association between the additional userrelationship and the second connection between the broker proxy serverand the trading system; wherein the established additional userrelationship and the established additional association allow the thirduser to engage in trading activity in the trading system on behalf ofthe second user via the second connection.
 32. The method of claim 31,wherein the third user is a broker that is prevented from engaging intrading activity via the trading network on behalf of itself.
 33. Themethod of claim 23, further comprising: receiving from the clientapplication a first network login request for a first user, the firstnetwork login request including first authentication information;approving the first network login request based at least on the receivedfirst authentication information, wherein approving the first networklogin request authorizes the first user to access the trading network;and identifying from a plurality of users one or more associated users,including the second user, for which the first user is authorized to acton behalf of.
 34. The method of claim 33, further comprising:identifying, based at least on the received first authenticationinformation, one or more trading systems to which the first user isauthorized access, the one or more trading systems including theparticular trading system; and communicating to the client application alist of the identified trading systems.
 35. The method of claim 33,wherein the first user is a first broker; wherein the method furthercomprises storing a set of broker-trader relationships, eachbroker-trader relationship defining a relationship between one of aplurality of brokers and one of a plurality of traders, the plurality ofbrokers including the first broker and the plurality of tradersincluding the second user; and wherein the one or more associated usersfor which the first user is authorized to act on behalf of areidentified by identifying from the set of broker-trader relationshipseach broker-trader relationship between the first broker and any one ofthe plurality of traders.
 36. The method of claim 23, furthercomprising: receiving a logoff notification that the first user islogged off of the trading network; in response to receiving the logoffnotification, detaching the second user from the first user by removingfrom storage the user relationship between the first user and the seconduser.
 37. The method of claim 36, further comprising: after removing therelationship from storage, receiving a logon notification that the firstuser is logged on to the trading network; and in response to receivingthe logon notification, automatically re-attaching the first user to thesecond user at least by re-establishing and re-storing the userrelationship between the first user and the second user.
 38. The methodof claim 23, further comprising: receiving from the client application afirst network login request for a first user, the first network loginrequest including first authentication information; approving the firstnetwork login request based at least on the received firstauthentication information, wherein approving the first network loginrequest authorizes the first user to access the trading network;identifying from a plurality of users one or more associated users,including the second user, for which the first user is authorized to actas a proxy; obtaining user profile information for the second user, theuser profile information including information regarding the second userthat can be used to allow the first user to engage in trading activityvia the trading network on behalf of the second user; and communicatingthe user profile information to the client application.
 39. A system ofmanaging access to a trading network, the system comprising a brokerproxy server operable to: receive at a broker proxy server an attachmentrequest from a client application associated with a first user, theattachment request including a request to attach the first user to asecond user, the attachment request indicating whether the second useris a passive trader or an active trader; establish and storing a userrelationship between the first user and the second user; if theattachment request indicates that the second user is a passive trader,establish a first association between the user relationship and a firstconnection between the broker proxy server and a trading system; whereinthe established user relationship and the established first associationallow the first user to engage in trading activity in the trading systemon behalf of the second user via the first connection; and if theattachment request indicates that the second user is an active trader:determine whether the second user is logged into the trading system; andif it is determined that the second user is logged into the tradingsystem, establish a second association between the user relationship anda second connection between the broker proxy server and the tradingsystem; wherein the established user relationship and the establishedsecond association allow the first user to engage in trading activity inthe trading system on behalf of the second user via the secondconnection.
 40. The system of claim 39, wherein the first connection andthe second connection are the same connection such that an associationis established between the user relationship and a particular connectionbetween the broker proxy server and the trading system regardless ofwhether the second user is a passive trader or an active trader.
 41. Thesystem of claim 39, wherein if it is determined that the second user isnot logged into the trading system, the broker proxy server is furtheroperable to: wait to receive a trading system login request from thesecond user; receive the trading system login request from the seconduser; and in response to receiving the trading system login request fromthe second user, establish a third association between the userrelationship and a third connection between the broker proxy server andthe trading system; wherein the established user relationship and theestablished third association allow the first user to engage in tradingactivity in the trading system on behalf of the second user via thethird connection.
 42. The system of claim 41, wherein the thirdconnection and the second connection are the same connection such thatan association is established between the user relationship and aparticular connection between the broker proxy server and the tradingsystem regardless of whether the second user is logged in at the timethe attachment request is received or logs in at a later time.
 43. Thesystem of claim 39, wherein the first user is a broker that is preventedfrom engaging in trading activity via the trading network on behalf ofitself.
 44. The system of claim 39, wherein the broker proxy server isfurther operable to determine whether the second user is authorized toattach to the first user.
 45. The system of claim 44, whereindetermining whether the second user is authorized to attach to the firstuser comprises: communicating an attachment authorization query to anauthentication manager, the attachment authorization query identifyingthe second user and the first user; and receiving from theauthentication manager a determination of whether the second user isauthorized to engage in trading activity on behalf of the first user.46. The system of claim 39, wherein the broker proxy server is furtheroperable to: receive an additional attachment request from an additionalclient application associated with a third user, the additionalattachment request including a request to attach the third user to asecond user; establish and storing an additional user relationshipbetween the third user and the second user; if the first association isestablished, establish an additional association between the additionaluser relationship and the first connection between the broker proxyserver and the trading system; wherein the established additional userrelationship and the established additional association allow the thirduser to engage in trading activity in the trading system on behalf ofthe second user via the first connection; and if the second associationis established, establish an additional association between theadditional user relationship and the second connection between thebroker proxy server and the trading system; wherein the establishedadditional user relationship and the established additional associationallow the third user to engage in trading activity in the trading systemon behalf of the second user via the second connection.
 47. The systemof claim 46, wherein the third user is a broker that is prevented fromengaging in trading activity via the trading network on behalf ofitself.
 48. The system of claim 39, further comprising an authenticationmanager operable to: receive from the client application a first networklogin request for a first user, the first network login requestincluding first authentication information; approve the first networklogin request based at least on the received first authenticationinformation, wherein approving the first network login requestauthorizes the first user to access the trading network; and identifyfrom a plurality of users one or more associated users, including thesecond user, for which the first user is authorized to act on behalf of.49. The system of claim 39, wherein the broker proxy server is furtheroperable to: receive a logoff notification that the first user is loggedoff of the trading network; in response to receiving the logoffnotification, detach the second user from the first user by removingfrom storage the user relationship between the first user and the seconduser.
 50. The system of claim 49, wherein the broker proxy server isfurther operable to: receive a logon notification that the first user islogged on to the trading network; and in response to receiving the logonnotification, automatically re-attach the first user to the second userat least by re-establishing and re-storing the user relationship betweenthe first user and the second user.
 51. The system of claim 39, furthercomprising an authentication manager operable to: receive from theclient application a first network login request for a first user, thefirst network login request including first authentication information;approve the first network login request based at least on the receivedfirst authentication information, wherein approving the first networklogin request authorizes the first user to access the trading network;identify from a plurality of users one or more associated users,including the second user, for which the first user is authorized to actas a proxy; obtain user profile information for the second user, theuser profile information including information regarding the second userthat can be used to allow the first user to engage in trading activityvia the trading network on behalf of the second user; and communicatethe user profile information to the client application.